cc @CyberShadow

OK. Wasn't trying to stir anything up, just a bit confused :)

Test failures due to code.dlang.org not being reachable intermediately.

So I rebased this to master to retrigger the CIs.

1. Imho the status before with more selective import was better and if we do such changes I would prefer if we do them automated ;-)
2. For this sole time it's safe to ignore CircleCi as it tries to checkout this branch at DMD/Druntime and fails to do so. We should probably add some fallback code to master if the base_branch does exist at the other repos.

For this sole time it's safe to ignore CircleCi as it tries to checkout this branch at DMD/Druntime and fails to do so.

-> #4996

However

It turns out that the changing the selective import import std.meta : AliasSeq to a module-wide import std.meta; exposed leaked import symbols as e.g std.range as it publicly imports std.array.

As a consequence it was possible to use AliasSeq by importing std.range and someone did in the meantime - thus our CI errored correctly:

out/std_range_package.d(884): Error: template instance AliasSeq!(byte, ubyte, short, ushort, int, uint, long, ulong) template 'AliasSeq' is not defined
out/std_range_package.d(980): Error: template instance AliasSeq!(byte, ubyte, short, ushort, int, uint, long, ulong) template 'AliasSeq' is not defined

See #4981 for a fix.